Build from from rootfs.tar system files
#978
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jjcarstens
changed the title
squashfs and erofs filesytems for firmwarerootfs.tar system files
jjcarstens
force-pushed
the
firmware-build-from-tar
branch
2 times, most recently
from
3090116 to
a19d3d5
Compare
|
Cool! Thank you. I believe tar_merger is still private so I'll copy over and rename. It has a number of deficiencies that I forgot to tell you about but it's getting close and this will definitely help me. |
jjcarstens
force-pushed
the
firmware-build-from-tar
branch
from
a19d3d5 to
0c20641
Compare
|
I added a few more notes. This could probably be split into 2 PRs for the EROFS concern, but after the redact that piece is so small that it could really go either way ¯_(ツ)_/¯ I've tested manually, but probably worth adding some tests if I can think of a good way how |
Starts support to allow building firmware from a `rootfs.tar` tarball file more efficiently in Elixir, rather than relying on bash scripts to unsquash, combine, and resquash an FS. It also adjusts the build process to allow using EROFS instead of squashfs when making the firmware
jjcarstens
force-pushed
the
firmware-build-from-tar
branch
from
0c20641 to
320e9ab
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starts support to allow building firmware from a
rootfs.tartarball file more efficiently in Elixir, rather than relying on bash scripts to unsquash, combine, and resquash an FS.The
mix firmwaretask was due for a good refactoring, so it looks like a lot. The old way of building is maintained for the typicalrootfs.squashfsfile that systems have traditionally provided.It also adjusts the build process to allow using EROFS instead of squashfs when making the firmware
Note
This adds
config :nerves, :firmware, fs_type: :erofsto specify to use EROFS. If there is a preferred option name and/or location, let me knowOther pieces to still consider:
scrub-otp-release.sh)*.imgfirmware file like the end ofrel2fw.shechostatements fromrel2fw.sh